Release 10.1A: OpenEdge Development:
Progress Dynamics Basic Development

Action security

Actions let you define security at the level of an individual visual object in your application or in the framework itself. This can be a toolbar button or a tab on a folder. It can also be the built in actions Add, Cancel, Copy, Delete, Modify, and View. You can define security for all occurrences of an action or you can qualify it for a particular product module, container, or instance attribute (or any combination of these).

Security allocations of this type have the following effects:

Revoke model — Prevents a user or a group from accessing a defined action. By default, Progress Dynamics allows access to all actions.
Grant model — Allows a user or group to access a defined action. By default, Progress Dynamics prevents all users from accessing actions.

Defining actions for items (menu items and toolbar buttons) is an alternative to defining menu item security. Use actions if you want to apply the security only to a specific container or module. In addition, the effect of applying menu item security is different from applying action security. Menu item security disables items, but they are still visible. Action security removes them from view.